Pod bay and vehicle docking

ABSTRACT

A pod bay for receiving at least one transportation vehicle for connection with at least one airdock in a high-speed, low-pressure transportation system, wherein the airdock provides a pathway for off-loading and loading of passengers and/or cargo to the transportation vehicle. The pod bay includes a housing and at least one airdock. The pod bay is operable to maintain the transportation vehicle in a low-pressure environment of the transportation system while connecting the transportation vehicle via the at least one airdock to a boarding area.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims the benefit of U.S. Provisional Application No. 63/018,398, filed Apr. 30, 2020, the contents of which are expressly incorporated herein by reference in their entirety.

BACKGROUND OF THE DISCLOSURE 1. Field of the Disclosure

The present disclosure relates to a Pod Bay, and more specifically relates to a Pod Bay for a transportation vehicle for a high-speed low-pressure transportation system.

2. Background of the Disclosure

As the development of high-speed low-pressure transportation systems continue, problems as to how a Pod connects with a transportation system station for off-loading passengers and/or cargo need to be solved.

Thus, there is a need for a system for connecting a Pod with a transportation system station for off-loading passengers and/or cargo need to be solved for a Pod in a high-speed low-pressure transportation system.

SUMMARY OF THE EMBODIMENTS OF THE DISCLOSURE

Aspects of the disclosure are directed to a system for connecting a Pod with a transportation system station for off-loading passengers and/or cargo need to be solved for a Pod in a high-speed low-pressure transportation system. The Pod Bay is operable to maintain the transportation vehicle in a low-pressure environment while connecting the Pod to a pathway for off-loading and on-barding of passengers and/or cargo and while transferring resources to the Pod

By implementing aspects of the disclosure, the Pod and transportation system station are connected to provide a structural path for on- and off-loading passengers and/or cargo, without needing to pressurize the entire volume surrounding the Pod, thus decreasing cycling time for Pod receiving and sending.

Aspects of the disclosure are directed to a pod bay for receiving at least one transportation vehicle for connection with at least one airdock in a high-speed, low-pressure transportation system, wherein the airdock provides a pathway for off-loading and loading of passengers and/or cargo to the transportation vehicle. The pod bay comprises a housing and at least one airdock, wherein the pod bay is operable to maintain the transportation vehicle in a low-pressure environment of the transportation system while connecting the transportation vehicle via the at least one airdock to a boarding area.

In embodiments, an internal volume of the airdock is operable to cycle between the low-pressure environment of the transportation system and a pressure of the boarding area.

In further embodiments, the pressure of the boarding area is an ambient pressure.

In additional embodiments, the at least one air dock comprises two air docks, and wherein the pod bay is configured to connect the two airdocks to the transportation vehicle.

In yet further embodiments, the pod bay is operable to receive a plurality of transportation vehicles in batch groupings.

In some embodiments, the pod bay further comprises one or more connectors operable to transfer resources to the transportation vehicle.

In embodiments, one or more connectors comprise resource transfer manifolds arranged on a ceiling of the pod bay so as to connect with an upper surface of the transportation vehicle.

In further embodiments, the pod bay further comprises at least one track operable to support the transportation vehicle.

In additional embodiments, the at least one track is operable to support the transportation vehicle in a levitated state relative to the at least one track.

In yet further embodiments, the at least one track is operable to support the transportation vehicle in a landed state on the at least one track.

Additional aspects of the disclosure are directed to a portal branch for receiving a plurality of transportation vehicles in the high-speed, low-pressure transportation system, the portal branch comprising a plurality of pod bays, wherein the plurality of pod bays are provided along a shared transportation vehicle path so that a plurality of transportation vehicles are connectable to the plurality of pod bays in batch groupings.

In embodiments, the portal branch comprises a passenger platform arranged adjacent the shared transportation path, the passenger platform providing the loading area for each of the pod bays.

In further embodiments, the portal branch comprises a gate valve at each end of the shared transportation path.

Additional aspects of the disclosure are directed to a transportation station for off-loading and loading of passengers and/or cargo to a transportation vehicle. The station comprises a receiving passage for receiving incoming transportation vehicles, a departing passage for sending outgoing transportation vehicles, and a plurality of the portal braches, each connected to the receiving passage and the departing passage.

In embodiments, respective shared transportation paths of the plurality of portal branches extend parallel to each other.

Additional aspects of the disclosure are directed to a method of operating a pod bay in a high-speed, low-pressure transportation system. The method comprises receiving a transportation vehicle in the pod bay and connecting at least one airdock arranged in the pod bay with the transportation vehicle, wherein the airdock provides a pathway for off-loading and loading of passengers and/or cargo to the transportation vehicle. The pod bay is operable to maintain the transportation vehicle in a low-pressure environment of the transportation system while the transportation vehicle is connected via the airdock to a boarding area.

In embodiments, the connecting comprises attaining a soft capture between the airdock and the transportation vehicle and attaining a hard capture between the airdock and the transportation vehicle.

In further embodiments, the method further comprises cycling an internal volume of the airdock between the low-pressure environment of the transportation system and a pressure of the boarding area while the transportation vehicle is connected via the airdock.

In additional embodiments, the method further comprises opening a bulkhead door connecting the airdock to the boarding area once pressure in the internal volume of the airdock equalizes with the pressure of the boarding area and a pressure of an internal volume of the transportation vehicle.

In yet further embodiments, the at least one airdock comprises two airdocks per transportation vehicle.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features which are characteristic of the systems, both as to structure and method of operation thereof, together with further aims and advantages thereof, will be understood from the following description, considered in connection with the accompanying drawings, in which embodiments of the disclosure are illustrated by way of example. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only, and they are not intended as a definition of the limits of the disclosure. For a more complete understanding of the disclosure, as well as other aims and further features thereof, reference may be had to the following detailed description of the embodiments of the disclosure in conjunction with the following exemplary and non-limiting drawings wherein:

FIG. 1 shows an exemplary Pod Bay branch layout including an overhead view of an embodiment of two portal branches having eight Pod Bays and a cross-sectional view of the portal branches of the Pod Bay in accordance with aspects of the disclosure;

FIGS. 2A-2D show an exemplary and non-limiting Pod Bay process flow diagram in which the Pod lands first in accordance with aspects of the disclosure;

FIGS. 3A-3D show exemplary top views of a process of a Pod engaging with a Pod Bay airdock in accordance with aspects of the disclosure;

FIGS. 4A-4F show exemplary cross-sectional views of a Pod in a Pod Bay as the Pod connects with an extending airdock (or a plurality of airdocks) in accordance with aspects of the disclosure;

FIG. 5 shows various volumes of the Pod Bay and exemplary respective pressures in the various volumes prior to pressure equalization in accordance with aspects of the disclosure;

FIGS. 6A and 6B show an exemplary and non-limiting depiction of a Pod Bay transportation station, a Pod Bay branch of the Pod Bay transportation station, and a cross-sectional view of a Pod Bay of the Pod Bay branch in accordance with aspects of the disclosure;

FIG. 7 shows an exemplary Pod Bay in accordance with aspects of the disclosure;

FIGS. 8A and 8B show an exemplary and non-limiting Pod Bay and Pod Bay station elements in accordance with aspects of the disclosure;

FIG. 9 shows a sectional view of a Pod Bay with a Pod docked therein and connected to an airdock in accordance with aspects of the disclosure;

FIG. 10 shows an exemplary and non-limiting control structure for the Pod Bay systems in accordance with aspects of the disclosure;

FIGS. 11A and 11B show an exemplary and non-limiting Pod Bay process flow diagram 200 in accordance with aspects of the disclosure;

FIGS. 12A and 12B show exemplary Pod constraints when the Pod is arranged for landing and take-off and when the Pod is arranged for docking (or docked) in accordance with aspects of the disclosure; and

FIG. 13 shows an exemplary environment for practicing aspects of the present disclosure.

DETAILED DESCRIPTION OF THE EMBODIMENTS OF THE DISCLOSURE

The following detailed description illustrates by way of example, not by way of limitation, the principles of the disclosure. This description will clearly enable one skilled in the art to make and use the disclosure, and describes several embodiments, adaptations, variations, alternatives and uses of the disclosure, including what is presently believed to be the best mode of carrying out the disclosure. It should be understood that the drawings are diagrammatic and schematic representations of exemplary embodiments of the disclosure, and are not limiting of the present disclosure nor are they necessarily drawn to scale.

The novel features which are characteristic of the disclosure, both as to structure and method of operation thereof, together with further aims and advantages thereof, will be understood from the following description, considered in connection with the accompanying drawings, in which an embodiment of the disclosure is illustrated by way of example. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only, and they are not intended as a definition of the limits of the disclosure.

In the following description, the various embodiments of the present disclosure will be described with respect to the enclosed drawings. As required, detailed embodiments of the present disclosure are discussed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the embodiments of the disclosure that may be embodied in various and alternative forms. The figures are not necessarily to scale and some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present disclosure.

The particulars shown herein are by way of example and for purposes of illustrative discussion of the embodiments of the present disclosure only and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects of the present disclosure. In this regard, no attempt is made to show structural details of the present disclosure in more detail than is necessary for the fundamental understanding of the present disclosure, such that the description, taken with the drawings, making apparent to those skilled in the art how the forms of the present disclosure may be embodied in practice.

As used herein, the singular forms “a,” “an,” and “the” include the plural reference unless the context clearly dictates otherwise. For example, reference to “a magnetic material” would also mean that mixtures of one or more magnetic materials can be present unless specifically excluded. As used herein, the indefinite article “a” indicates one as well as more than one and does not necessarily limit its referent noun to the singular.

Except where otherwise indicated, all numbers expressing quantities used in the specification and claims are to be understood as being modified in all examples by the term “about.” Accordingly, unless indicated to the contrary, the numerical parameters set forth in the specification and claims are approximations that may vary depending upon the desired properties sought to be obtained by embodiments of the present disclosure. At the very least, and not to be considered as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should be construed in light of the number of significant digits and ordinary rounding conventions.

Additionally, the recitation of numerical ranges within this specification is considered to be a disclosure of all numerical values and ranges within that range (unless otherwise explicitly indicated). For example, if a range is from about 1 to about 50, it is deemed to include, for example, 1, 7, 34, 46.1, 23.7, or any other value or range within the range.

As used herein, the terms “about” and “approximately” indicate that the amount or value in question may be the specific value designated or some other value in its neighborhood. Generally, the terms “about” and “approximately” denoting a certain value is intended to denote a range within ±5% of the value. As one example, the phrase “about 100” denotes a range of 100 ±5, i.e. the range from 95 to 105. Generally, when the terms “about” and “approximately” are used, it can be expected that similar results or effects according to the disclosure can be obtained within a range of ±5% of the indicated value.

As used herein, the term “and/or” indicates that either all or only one of the elements of said group may be present. For example, “A and/or B” shall mean “only A, or only B, or both A and B”. In the case of “only A”, the term also covers the possibility that B is absent, i.e. “only A, but not B”.

The term “substantially parallel” refers to deviating less than 20° from parallel alignment and the term “substantially perpendicular” refers to deviating less than 20° from perpendicular alignment. The term “parallel” refers to deviating less than 5° from mathematically exact parallel alignment. Similarly “perpendicular” refers to deviating less than 5° from mathematically exact perpendicular alignment.

The term “at least partially” is intended to denote that the following property is fulfilled to a certain extent or completely.

The terms “substantially” and “essentially” are used to denote that the following feature, property or parameter is either completely (entirely) realized or satisfied or to a major degree that does not adversely affect the intended result.

The term “comprising” as used herein is intended to be non-exclusive and open-ended. Thus, for example a composition comprising a compound A may include other compounds besides A. However, the term “comprising” also covers the more restrictive meanings of “consisting essentially of” and “consisting of”, so that for example “a composition comprising a compound A” may also (essentially) consist of the compound A.

The various embodiments disclosed herein can be used separately and in various combinations unless specifically stated to the contrary.

Embodiments of the present disclosure may be used in a low-pressure high-speed transportation system, for example, as described in commonly-assigned U.S. Pat. No. 9,718,630, titled “Transportation System,” the contents of which are hereby expressly incorporated by reference herein in their entirety. For example, the segmental tube structure may be used as a transportation path for a low-pressure, high-speed transportation system. In embodiments, a low-pressure environment within a sealed tubular structure may be approximately 100 Pa. Additionally, embodiments of the present disclosure may be used with airdock assembly methods and systems, for example, as described in commonly-assigned Patent Application No. ______ (Attorney Docket No. P62099), titled “Airdock Assembly,” soft capture methods and systems, for example, as described in commonly-assigned Patent Application No. ______ (Attorney Docket No. P62100), titled “Airdock Soft Capture,” and Pod Bay and docking systems and methods, for example, as described in commonly-assigned International Patent Application No. ______ (Attorney Docket No. P62101), titled “Airdock Hard Capture,” filed on even date herewith, the contents of each of which are hereby expressly incorporated by reference herein in their entireties.

In accordance with aspects of the disclosure, the Pod Bay is a station where passengers and/or cargo, and resources are transferred to the Pod (or transportation vehicle). More specifically, the Pod Bay is where passengers embark onto/disembark from the Pod while, in accordance with aspects of the disclosure, the Pod remains in a vacuum (or near vacuum) environment. With an exemplary and non-limiting embodiment, each Pod Bay has two airdocks. An airdock is where each of the Pod doors is aligned to transfer passengers and cargo to and from the Pod. In accordance with aspects of the disclosure, airdock mechanisms align the Pod doors to respective airdocks. A Resource Transfer System (RTS) is used to replenish a Pod with resources (such as battery charge and breathable air, for example) while the Pod is docked in the Pod Bay. A soft capture system is used once the Pod is parked. The soft capture system is used to close the gap between the Pod doors and respective airdock doors and align the two with each other. In embodiments, the alignment process may utilize two steps: rough alignment and final alignment.

A hard capture system is utilized once final alignment of the Pod and airdock doors is achieved. With an exemplary embodiment, the hard capture system maintains the Pod in fixed position relative to the airdock with a series of latches.

Once the Pod arrives at the assigned Pod Bay, the soft capture system moves the Pod towards the airdocks so that the Pod and mating airdocks are properly aligned. With an exemplary embodiment, the soft capture process will move the Pod in the Y-direction (or approximate Y-direction) by approximately 250 mm. Once alignment is confirmed, the hard capture latches engage with the respective catches on the Pod. The hard capture process ensures sealing between the Pod and airdock. Once pressures of different volumes (e.g., airdock volume, interstitial volume, Pod cabin volume) are equalized within an acceptable range, the doors open to transfer passengers. For take-off, the general sequence is the reverse of the steps described above.

As described further below, the Pod Bay is a building block of a portal branch system, wherein each portal may have multiple portal branches, and there may be multiple Pod Bays within a portal branch to meet the required throughput demand. One or more airdocks are arranged in the Pod Bay, wherein each airdock is a structure that connects the Pod door to Pod Bay door of the Pod Bay.

FIG. 1 shows an exemplary Pod Bay branch layout including an overhead view of an embodiment of two portal branches 105 having eight Pod Bays 100 and a cross-sectional view of the portal branches of the Pod Bay in accordance with aspects of the disclosure. As shown in FIG. 1 , a plurality of Pods 110 may be parked at respective airdocks 115 (or pairs of airdocks 115) arranged at the Pod Bays 100, wherein each airdock 115 is a structure that connects the Pod door 120 to bulkhead door 125 of the Pod Bay 100. As shown in FIG. 1 , in embodiments the airdock 115 may also include an airdock door 122 adjacent the Pod door.

Each branch 105 of the Pod Bay 100 may include a platform 130 for passenger movement, including areas for passengers waiting, horizontal circulation regions, and a “stand clear” area. As shown in FIG. 1 , in accordance with aspects of the disclosure, the Pod 110 remains in a vacuum (or near vacuum) environment 135, while passengers embark onto and/or disembark from the Pod 120 via the airdock 115. The environment of the airdock cycles between the vacuum (or near vacuum) environment of the transportation tube, and an ambient pressure environment of the platform 130 to allow passengers to embark onto and/or disembark from the Pod 110 via the airdock 115.

In accordance with aspects of the disclosure, Pod resources, such as battery charge and breathable air, for example, are replenished while the Pod is in the Pod Bay. Additionally, trip data and waste water are transferred from the Pod to the wayside while Pod is parked in the Pod Bay. Track elements within the Portal Branch may be similar to the tube track elements of the transportation path. Speed of the Pod within the Portal Branch may be a relatively slower speed (e.g., 5 m/s).

In order to transfer passengers, the Pod will be assigned to a Pod Bay through command and control. In embodiments, a Pod with have two doors, and the two doors on the Pod and the two doors at the Pod Bay will be aligned properly prior to passenger transfer. Once all conditions are met, the doors of the Pod and the doors of the Pod Bay open for passenger dis/embarkation.

The primary function of the Pod Bay is to safely transfer passengers from the Pod/Portal to Portal/Pod. Depending upon the architecture selected, in embodiments, the Pod Bay operation includes following: Pod parking itself within an assigned Pod Bay, soft capture, Pod landing onto (or hovering below) levitation track, hard capture, pressure equalization.

Pod parking commences with the command and control communicating to the Pod the assigned Pod Bay location. Command and control is responsible for ensuring proper and safe movement of Pods, receiving status/data, making safety and mission critical decisions, and issuing commands to Pod and Operation Support System (OSS) to be carried out. OSS is responsible for the operational management of Portal and Depot, the central command of active wayside elements and providing communication network to support System operations.

Then, the Pod parks itself relative to the reference monument in the Pod Bay within a certain range. This reference is only in the direction of travel (X). The Pod levitation and guidance engines are already capable of maintaining the Pod position within a tight lateral (Y) and vertical (Z) envelope. A separate monument in the X direction may be necessary as the track system used for normal transportation may not maintain information on the Pod's global position. In embodiments, this monument should be sensed and measured by the Pod to enable braking, positioning and landing within the capture envelope. With the Pod's landing accuracy of +/−50 mm currently assumed along with manufacturing tolerances, the capture envelope should be able to accommodate +/−72 mm in the X direction, and is able to accommodate larger or smaller distances.

Depending upon the architecture selected, once the Pod is parked within the Pod Bay, the soft capture system brings the Pod towards the airdock doors by either pulling or pushing the Pod in Y direction, and then aligning the Pod doors to the airdock doors. The soft capture system should be able to accommodate variations in relative positioning of the Pod doors and Pod Bay doors due to manufacturing variation, thermal and pressure effect as well as the Pod's parking accuracy.

In contemplated embodiments, the soft capture system may include the following subassemblies: soft capture mechanisms, final kinematic alignment features, compliant element between the airdock door and Portal, and airdock mass offloading system. The soft capture mechanism, which in embodiments, may be a set of tension cables, or actuator, moves the Pod towards the airdock doors. The final alignment elements on the Pod and Pod Bay are intended to ensure the respective doors at both locations are properly aligned during the soft capture process. The airdock doors may be housed within the airdock structure, which is connected to the Portal Branch by a Flex Joint. The airdock structure should be supported such that the airdock doors can be aligned to the respective Pod doors while accommodating expected variations described above, and Flex Joint is intended to allow such adjustability.

Once soft capture completion is detected, in embodiments, the Pod will land up against the solid levitation/landing track (wherein airdocks may be pulled by ˜15 mm as the Pod pulls up). (With other contemplated embodiments, the Pod may remaining hovering. And with yet further contemplated embodiments, the Pod may land first before soft capture.) Upon landing, the Pod can either communicate directly to the Pod Bay that it is in a ready state for hard capture, or the Pod Bay can sense that the Pod is properly positioned and ready for hard capture. In contemplated embodiments, this could be accomplished by sensing that the levitation gap is closed with a proximity sensor and/or measuring the position of some Pod side reference target to confirm that the Pod is within the capture envelope.

In accordance with aspects of the disclosure, once soft capture is attained, the hard capture process commences. In embodiments, the hard capture system may include an array of latches and seals that close the gap between the Pod fuselage and airdock structure. The latching positions align with the Pod door stops on the Pod door frame so that the door plug load is transferred to the Pod Bay/airdock through the same locations when the pressure differential across the Pod door/door opening is removed. The latch/door stop positions are placed at the intercostals of the fuselage, and with an exemplary and non-limiting embodiment, there may be sixteen latches per door, with eight on each side.

In accordance with aspects of the disclosure, when engaged, the latches provide the primary load path to react the door plug load when the pressure differential across the Pod door/door opening is removed. The latches also provide the load to keep the seals compressed. In some embodiments, the soft capture system may be sized to act as a secondary load path in case of significant latch array failure. Once all the latches are confirmed to be engaged, the pressure equalization process is initiated.

In the Portal Branch, there may be five pressure volumes (Portal volume, Walkway volume, Interstitial volume, Portal Branch volume and Pod volume). The interstitial volume is the small volume that is trapped between the airdock door and Pod fuselage when the Pod is fully captured. The Walkway volume is the volume between the airdock door 910 and the portal door 905. The airdock door has been added primarily as a redundant wayside barrier between the portal and the vacuum environment to ensure passenger and staff safety. A number of failure modes can be mitigated greatly by including a redundant wayside door. Additionally, outfitting the airdock with a door at its end significantly reduces the mass of air vented to the vacuum environment during the undocking phase, which is an important consideration for minimizing the burden on the Pressure Management System and minimizing the docking cycle time.

Upon completion of the of the hard capture, the Pod, the interstitial volume and the walkway (or airdock) volume need to be equalized within a certain range prior to opening the doors for passenger safety. In embodiments, the interstitial volume is pressurized through vent valve(s) while the Pod and airdock walkway volume pressures equalize. In contemplated embodiments, the Pod—Walkway (Portal) volume pressure equalization may take place within the airdock or through different ports, which may depend on the Pod design. Once pressures are equalized (within tolerance), the airdock door opens first, followed by the opening of the Pod and Portal (or bulkhead) door open simultaneously.

Prior to undocking, the Pod and Portal doors close first, then the airdock door closes. Then, the air trapped in the interstitial volume is released into the Portal Branch vacuum. After the doors close upon completion of dis/embarkation process, the Pod pushes itself off of the levitation/landing track (unless the Pod is configured to remain hovering the whole time, in which case a push off the track is unnecessary) and the soft capture mechanism will bring (or allow to move via gravity) the Pod back in the take-off position.

In accordance with aspects of the disclosure, the Pod Bay should minimize cycle time to maintain the required throughput of the Portal without driving a need for more Pod Bays within a limited footprint. With an exemplary and non-limiting embodiment, cycle time may be 60 seconds for the docking and undocking process combined. Here, cycle time starts right after the Pod is parked and ends when the Pod is ready to take off.

In view of the above, the Pod Bay system states may include:

Idle—Pod Bay in ready state. Idle Landed (or parked) Pod—Pod landed and within capture envelope. Captured Pod—Pod safely engaged with soft capture system Soft Capture Transition—Soft capture system is tensioned, drawing Pod from branch alignment to docking alignment. Docked, Soft capture—Pod is engaged with airdock kinematic hard points. Docked, Hard capture—Pod is latched with 16+ latches per Pod door. Docked, Seal inflation—Inflatable seals between the Pod and airdock are being inflated. Docked, airdock volume (volume between airdock door and Pod door) being pressurized—Atmospheric pressure air is being provided to the airdock volume. Docked, pressures equalized—Portal, airdock tunnel, airdock and Pod pressures are equalized to some tolerance. Docked, doors open—doors open to allow passenger disembarkation and boarding.

FIGS. 2A-2D show an exemplary and non-limiting Pod Bay process flow diagram 200 in which the Pod lands first in accordance with aspects of the disclosure. As shown in FIGS. 2A-2D, the operation support system functions are shown in column 205, the Pod controller operations are shown in column 210, the Pod Bay controller operations are shown in column 215, and the hard/soft capture, door, and pressure equalization operations are shown in column 220. Additionally, as shown in FIG. 2A, an exemplary process for the Pod entering the Pod Bay is shown in row 225. As shown in FIGS. 2B and 2C, an exemplary process for the Pod docking in the Pod Bay is shown in row 230. As shown in FIG. 2D, an exemplary process for the embarking (and disembarking) to (or from) the Pod docked in the Pod Bay is shown in row 235, an exemplary process of the Pod undocking in the Pod Bay is shown in row 240, and an exemplary process for the Pod exiting the Pod Bay is shown in row 245.

FIGS. 3A-3D show exemplary top views of a process of a Pod 110 engaging with a Pod Bay airdock 115 in accordance with aspects of the disclosure. As shown in FIG. 3A, the Pod 110 approaches the airdock 115 of the Pod Bay and, in embodiments, the Pod 110 lands upwardly onto the transportation tracks, or in other embodiments, the Pod 110 hovers (or levitates) below the transportation tracks. As shown in FIG. 3B, a soft capture of the Pod 110 occurs, wherein the airdock 115 captures and draws the Pod 110 laterally, for example, toward the airdock 115 (as represented by the arrows). As shown in FIG. 3C, a hard capture of the Pod 110 occurs, wherein the airdock 115 latches to the Pod 110 and seals the airdock 115 to the Pod 110. As shown in FIG. 3D, once hard capture is achieved, the airdock 115 is flooded so that pressures are equalized between the pressure of the interior of the Pod 110 (and the pressure of the platform 130) and the pressure of the airdock 115. In other words, the pressure in the airdock 115 is raised to the pressure of the interior of the Pod 110 (and the pressure of the platform 130). Once pressure is equalized, the doors of the Pod and of the Pod Bay open to permit embarking (and dis-embarking) of passengers.

Pod parking commences with the command and control communicating to the Pod the assigned Pod Bay location. Command and control is responsible for ensuring proper and safe movement of Pods, receiving status/data, making safety and mission critical decisions, and issuing commands to Pod and Operation Support System (OSS) to be carried out. OSS is responsible for the operational management of portal and depot, the central command of active wayside elements and providing communication network to support system operations.

FIGS. 4A-4F show exemplary cross-section views of a Pod 110 in a Pod Bay 100 as the Pod 110 connects with an extending airdock 115 (or a plurality of airdocks 115) in accordance with aspects of the disclosure. With this exemplary embodiment, the airdock is moved towards the Pod (i.e., a move-the-airdock architecture). As should be understood, however, the disclosure contemplates a Pod Bay utilizing a move-the-pod architecture. As shown in FIG. 4A, when the Pod 110 arrives in the Pod Bay 100, the Pod door is closed, the bulkhead door is closed, and the airdock 115 is retracted from the Pod transportation path. With an exemplary embodiment, in an initial condition, the Pod is in a parked position sitting (or levitating) on the Pod Bay ceiling. With an exemplary embodiment, actuators are operable to jog the airdock 115 toward the Pod 110 and the actuators define the airdock location in the y-direction. At this stage, the airdock position in the x-direction, the z-direction rx (or rotational-x direction), ry, and rz directions are defined by the guideway the airdock 115 is arranged upon. As shown in FIG. 4A, at this stage the interior of the airdock 115 is at the same pressure as the low-pressure environment 135 of the transportation tube.

As shown in FIG. 4B, with this exemplary embodiment, the airdock 115 is extended and connected to the Pod 110 (via soft capture and then hard capture) to seal the interior of the airdock 115. During this process, an airdock alignment tool may interact with one or more Pod-side alignment features, such that the airdock position in the y-, z-, rx-, ry-, and rz-directions is now defined by the Pod itself, and the guideway location is no longer used a datum. The airdock halts once jogged to the specific Pod-dock position, and latches are initiated to engage Pod-side features. Jogging actuators are allowed to “float” and the airdock position relative to the Pod is defined by the latches. At this stage, the Pod door remains closed and the bulkhead door remains closed. The latches continue to actuate and the airdock is secured tightly to the Pod, with the seals arranged there between fully engaged, and the airdock is fully positioned. The jogging actuators are locked out in the sealing position and remain rigid for the remainder of the passenger egress/ingress operation. In accordance with aspects of the disclosure, the latches maintain the seal and the locked-out jogging actuators transfer the thrust load caused by the equalization from the Pod 110 to the Pod Bay.

As shown in FIG. 4C, once the interior of the airdock 115 is sealed, the interior of the airdock 115 is flooded so as to equalize the pressure between the interior of the airdock 115 and the interior of the Pod 110 (and the platform 130). As shown in FIG. 4D, once the pressure is equalized between the interior of the airdock 115 and the interior of the Pod 110 (and, in embodiments, the platform 130), pressure is checked, a safety protocol is passed, and the bulkhead door is opened to connect the air dock 115 with the platform 130. As shown in FIG. 4E, the Pod door is opened (and the Pod Bay door (not shown) is opened) to connect the airdock 115 with the interior of the Pod 110. As shown in FIG. 4F, once the Pod door is opened, passengers may exit the Pod 110 via the airdock 115 to the platform 130.

FIG. 5 shows various volumes of the Pod Bay and exemplary respective pressures in the various volumes prior to pressure equalization in accordance with aspects of the disclosure. In accordance with aspects of the disclosure, pressure equalization must be maintained between the portal, the tunnel, the airdock and the Pod. As shown in FIG. 5 , prior to pressure equalization, the pressure in the transportation tube or pressure in the Pod Bay vacuum structure (i.e., volume 2) is 100 Pa, the pressure in the airdock (i.e., volume 3) is 100 Pa, and the pressure in the airdock tunnel (i.e., volume 4) is also 100 kPa. In contrast, as shown in FIG. 5 , the pressure in the Pod interior (i.e., volume 1) is 100 kPa and the pressure in the portal (or platform area) (i.e., volume 5) is also 100 kPa. After pressure equalization, the pressure in the airdock (i.e., volume 3) is also raised to 100 kPa, while the pressure in the transportation tube (i.e., volume 2) remains at 100 Pa, so that the pressures in volumes 1, 3, 4, and 5 are equalized. In such a manner, in accordance with aspects of the disclosure, a much smaller volume is cycled between the low-pressure of the transportation tube (or the Pod Bay vacuum structure) and the ambient pressure of the station passenger area.

The Pod Bay is operable to manage the pressure in the airdock tunnel and the airdock volumes. With an exemplary and non-limiting embodiment, the airdock tunnel (i.e., volume 4) and airdock volumes (i.e., volume 3) are 1.6 m³ and 0.7 m³, respectively. In contrast, the volume of the Pod Bay vacuum structure (i.e., volume 2) is much larger than the volume of the Pod (i.e., volume 1), and the volume of the portal (or station passenger area) is relatively infinite. In embodiments, the venting cascades in series from the portal through the airdock tunnel to the airdock.

In nominal operations, the airdock tunnel pressure is held constant despite leakage. The airdock (i.e., volume 3) completes a full 100 Pa to 101 kPa per cycle. In contemplated embodiments, during undocking, air in the airdock may first be vented through a valve into the vacuum environment in a controlled manner, and then the remainder of the air may be vented to the vacuum environment when breaking the seal between the Pod and the airdock. In order to equalize the airdock volume to atmospheric pressure within the desired cycle time, the vent valve may be at least 75 mm in diameter. The overall time it takes for pressure equalization should also account for valve actuation time.

FIGS. 6A and 6B show an exemplary and non-limiting depiction of a Pod Bay transportation station 600, a Pod Bay branch 105 of the Pod Bay transportation station 600, and a cross-sectional view of a Pod Bay 100 of the Pod Bay branch 105 in accordance with aspects of the disclosure. As shown in FIG. 6A, the Pod Bay transportation station 600 is a station where passengers and/or cargo along with resources (e.g., air, power, etc.) are transferred to the Pod (not shown). A replenishment system recharges (e.g., battery power, oxygen, etc.) the Pod (not shown) while it is docked at the Pod Bay 100. The airdock enables a bridge from the portal to the Pod through the vacuum environment for safe passenger transfer.

As shown in the cross-section view of FIG. 6B, the Pod Bay 100 includes an airdock 115, having an airdock door, a latching mechanism (e.g., for hard capture), a seal for a sealing connection between the airdock 115 and the Pod (not shown), and a portal door connecting the airdock 115 with the passenger waiting area (not shown). Additionally, as shown in FIG. 6B, a track (e.g., a pair of parallel levitation tracks) is arranged on an interior roof of the Pod Bay 100, which allows the Pod (not shown) to be moved into and out of the Pod Bay 100. While not shown in FIG. 6B, it should be understood that additional elements (e.g., propulsion track, guidance track and/or braking tracks) may also be arranged in the Pod Bay 100.

FIG. 7 shows an exemplary Pod Bay 100 in accordance with aspects of the disclosure. As shown in FIG. 7 , the Pod Bay 100 includes, for example, two airdocks 115 for connection with two corresponding doors of a Pod (not shown) docked in the Pod Bay 100. Additionally, as shown in FIG. 7 , the Pod Bay 100 includes one or more resource transfer manifolds 705, which are operable to connect with a Pod (not shown) when docked in the Pod Bay 100 so as to allow for transfer of resources (e.g., power, oxygen, waste, etc.).

FIGS. 8A and 8B show an exemplary Pod Bay 100 and Pod Bay station elements in accordance with aspects of the disclosure. For example, as shown in FIGS. 8A and 8B, in contemplated embodiments, the Pod Bay 100 may be arranged atop a utility room 805 (which may house batteries or generators for charging the Pod (not shown) and/or oxygen tanks for supplying oxygen tanks on the Pod (not shown) when arranged in the Pod Bay 100. As also shown in FIGS. 8A and 8B, a passenger platform 130 is arranged adjacent the Pod Bay 100 and, in embodiments, may be arranged above the utility room 805. FIG. 8A shows a fare check system 810 may be arranged by the portal door. FIG. 8A also shows that the Pod Bay station may include architectural facades 815 around the Pod Bay 100 so as to improve the aesthetic appearance of the Pod Bay 100.

FIG. 9 shows a perspective view of a Pod Bay 900 with a Pod 110 docked therein and connected to an airdock 115 in accordance with aspects of the disclosure. As shown in FIG. 9 , with the Pod 110 docked to the airdock 115 of the Pod Bay 900, an interstitial volume 935 is formed between the Pod 110 (or Pod door 915) and the airdock door 910. FIG. 9 also shows the Pod branch volume 940 surrounding the Pod 110 in the Pod Bay and the walkway volume 930 of the airdock 115. A portal door 905 is arranged between the passenger waiting area 130 and the walkway volume 930 of the airdock 115. As also shown in FIG. 9 , in embodiments, the Pod 110 may include one or more egress doors 920 (e.g., emergency egress doors) at the longitudinal ends of the Pod 110 connecting the Pod cabin 950 with the exterior of the Pod 110.

FIG. 10 shows an exemplary and non-limiting control structure 1000 for the Pod Bay systems in accordance with aspects of the disclosure. As shown in FIG. 10 , a Pod Bay controller 1005 communicates with airdock controllers 1010 (e.g. two airdock controllers 1010), a track hanger controller 1015, and a resource transfer controller 1020. The Pod Bay controller 1005 also communicates with a Pod controller 1025 and a portal operational support system 1035. A portal command and control 1030 also communicates with the portal operational support system 1035 and the Pod controller 1025. The Pod controller 1025 is also in communication with the resource transfer controller 1020.

FIGS. 11A and 11B show an exemplary and non-limiting Pod Bay process flow diagram 1100 in accordance with aspects of the disclosure. As shown in FIGS. 11A and 11B, the operation support system functions are shown in column 205, the Pod controller operations are shown in column 210, the Pod Bay controller operations are shown in column 215, and the hard/soft capture, door, and pressure equalization operations are shown in column 220. Additionally, as shown in FIG. 11A, an exemplary process for the Pod entering the Pod Bay is shown in row 225. As shown in FIGS. 11A and 11B, an exemplary process for the Pod docking in the Pod Bay is shown in row 230. As shown in FIG. 11B, an exemplary process for the embarking (and disembarking) to (or from) the Pod docked in the Pod Bay is shown in row 235, an exemplary process of the Pod undocking in the Pod Bay is shown in row 240, and an exemplary process for the Pod exiting the Pod Bay is shown in row 245.

FIGS. 12A and 12B show exemplary Pod constraints when the Pod is arranged for landing and take-off and when the Pod is arranged for docking (or docked) in accordance with aspects of the disclosure. This embodiment may be used with the land-first option. As shown in FIG. 12A, when the Pod 110 is arranged for landing and take-off, the Pod is constrained (e.g., exactly constrained) in the x-, y-, and z-directions by the landing track 1210. For example, the landing track provides three Z constraints (X, Y and Rot Z free), two Y constraints, and an X constraint.

In contrast, in accordance with aspects of the disclosure, as shown in FIG. 12B, when the Pod 110 is arranged for docking (or docked), the Pod is constrained (e.g., exactly constrained) by both the landing track 1210 and the Pod 110. For example, the landing track provides three Z constraints (X, Y and Rot Z free), and the Pod is constrained (via hard capture) at the doors with one X constraint and two Y constraints.

While the specification describes particular embodiments of the present disclosure, those of ordinary skill can devise variations of the present disclosure without departing from the inventive concept.

System Environment

Aspects of embodiments of the present disclosure (e.g., control systems for the Pod Bay) can be implemented by such special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions and/or software, as described above. The control systems may be implemented and executed from either a server, in a client server relationship, or they may run on a user workstation with operative information conveyed to the user workstation. In an embodiment, the software elements include firmware, resident software, microcode, etc.

As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, a method or a computer program product. Accordingly, aspects of embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present disclosure (e.g., control systems) may take the form of a computer program product embodied in any tangible medium of expression having computer-usable program code embodied in the medium.

Any combination of one or more computer usable or computer readable medium(s) may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CDROM), an optical storage device, a transmission media such as those supporting the Internet or an intranet, a magnetic storage device, a usb key, and/or a mobile phone.

In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave. The computer usable program code may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network. This may include, for example, a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). Additionally, in embodiments, the present disclosure may be embodied in a field programmable gate array (FPGA).

FIG. 13 is an exemplary system for use in accordance with the embodiments described herein. The system 3900 is generally shown and may include a computer system 3902, which is generally indicated. The computer system 3902 may operate as a standalone device or may be connected to other systems or peripheral devices. For example, the computer system 3902 may include, or be included within, any one or more computers, servers, systems, communication networks or cloud environment.

The computer system 3902 may operate in the capacity of a server in a network environment, or in the capacity of a client user computer in the network environment. The computer system 3902, or portions thereof, may be implemented as, or incorporated into, various devices, such as a personal computer, a tablet computer, a set-top box, a personal digital assistant, a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a personal trusted device, a web appliance, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that device. Further, while a single computer system 3902 is illustrated, additional embodiments may include any collection of systems or sub-systems that individually or jointly execute instructions or perform functions.

As illustrated in FIG. 13 , the computer system 3902 may include at least one processor 3904, such as, for example, a central processing unit, a graphics processing unit, or both. The computer system 3902 may also include a computer memory 3906. The computer memory 3906 may include a static memory, a dynamic memory, or both. The computer memory 3906 may additionally or alternatively include a hard disk, random access memory, a cache, or any combination thereof. Of course, those skilled in the art appreciate that the computer memory 3906 may comprise any combination of known memories or a single storage.

As shown in FIG. 13 , the computer system 3902 may include a computer display 3908, such as a liquid crystal display, an organic light emitting diode, a flat panel display, a solid state display, a cathode ray tube, a plasma display, or any other known display. The computer system 3902 may include at least one computer input device 3910, such as a keyboard, a remote control device having a wireless keypad, a microphone coupled to a speech recognition engine, a camera such as a video camera or still camera, a cursor control device, or any combination thereof. Those skilled in the art appreciate that various embodiments of the computer system 3902 may include multiple input devices 3910. Moreover, those skilled in the art further appreciate that the above-listed, exemplary input devices 3910 are not meant to be exhaustive and that the computer system 3902 may include any additional, or alternative, input devices 3910.

The computer system 3902 may also include a medium reader 3912 and a network interface 3914. Furthermore, the computer system 3902 may include any additional devices, components, parts, peripherals, hardware, software or any combination thereof which are commonly known and understood as being included with or within a computer system, such as, but not limited to, an output device 3916. The output device 3916 may be, but is not limited to, a speaker, an audio out, a video out, a remote control output, or any combination thereof. As shown in FIG. 13 , the computer system 3902 may include communication and/or power connections to a Pod Bay 100, and a Pod Bay controller 1305 to control the Pod Bay 100 in accordance with aspects of the disclosure. Additionally, as shown in FIG. 13 , the computer system 3902 may include one or more sensors 1310 (e.g., positional sensors, GPS systems, magnetic sensors) that may provide data (e.g., positional data) to the Pod Bay controller 1305.

Furthermore, the aspects of the disclosure may take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. The software and/or computer program product can be implemented in the environment of FIG. 13 . For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable storage medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk-read only memory (CD-ROM), compact disc-read/write (CD-R/W) and DVD.

Although the present specification describes components and functions that may be implemented in particular embodiments with reference to particular standards and protocols, the disclosure is not limited to such standards and protocols. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same or similar functions are considered equivalents thereof.

The illustrations of the embodiments described herein are intended to provide a general understanding of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Additionally, the illustrations are merely representational and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be minimized. Accordingly, the disclosure and the figures are to be regarded as illustrative rather than restrictive.

Accordingly, the present disclosure provides various systems, structures, methods, and apparatuses. Although the disclosure has been described with reference to several exemplary embodiments, it is understood that the words that have been used are words of description and illustration, rather than words of limitation. Changes may be made within the purview of the appended claims, as presently stated and as amended, without departing from the scope and spirit of the disclosure in its aspects. Although the disclosure has been described with reference to particular materials and embodiments, embodiments of the disclosure are not intended to be limited to the particulars disclosed; rather the disclosure extends to all functionally equivalent structures, methods, and uses such as are within the scope of the appended claims.

While the computer-readable medium may be described as a single medium, the term “computer-readable medium” includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The term “computer-readable medium” shall also include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the embodiments disclosed herein.

The computer-readable medium may comprise a non-transitory computer-readable medium or media and/or comprise a transitory computer-readable medium or media. In a particular non-limiting, exemplary embodiment, the computer-readable medium can include a solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium can be a random access memory or other volatile re-writable memory. Additionally, the computer-readable medium can include a magneto-optical or optical medium, such as a disk, tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium. Accordingly, the disclosure is considered to include any computer-readable medium or other equivalents and successor media, in which data or instructions may be stored.

While the specification describes particular embodiments of the present disclosure, those of ordinary skill can devise variations of the present disclosure without departing from the inventive concept.

One or more embodiments of the disclosure may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any particular disclosure or inventive concept. Moreover, although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the description.

The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments which fall within the true spirit and scope of the present disclosure. Thus, to the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Accordingly, the novel architecture is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.

While the disclosure has been described with reference to specific embodiments, those skilled in the art will understand that various changes may be made and equivalents may be substituted for elements thereof without departing from the true spirit and scope of the disclosure. While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the embodiments of the disclosure. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the disclosure. In addition, modifications may be made without departing from the essential teachings of the disclosure. Furthermore, the features of various implementing embodiments may be combined to form further embodiments of the disclosure.

Insofar as the description above and the accompanying drawing disclose any additional subject matter that is not within the scope of the claims below, the embodiments are not dedicated to the public and the right to file one or more applications to claim such additional embodiments is reserved. 

What is claimed is:
 1. A pod bay for receiving at least one transportation vehicle for connection with at least one airdock in a high-speed, low-pressure transportation system, wherein the airdock provides a pathway for off-loading and loading of passengers and/or cargo to the transportation vehicle, the pod bay comprising: a housing; and at least one airdock, wherein the pod bay is operable to maintain the transportation vehicle in a low-pressure environment of the transportation system while connecting the transportation vehicle via the at least one airdock to a boarding area.
 2. The pod bay of claim 1, wherein an internal volume of the airdock is operable to cycle between the low-pressure environment of the transportation system and a pressure of the boarding area.
 3. The pod bay of claim 2, wherein the pressure of the boarding area is an ambient pressure.
 4. The pod bay of claim 1, wherein the at least one air dock comprises two air docks, and wherein the pod bay is configured to connect the two airdocks to the transportation vehicle.
 5. The pod bay of claim 1, wherein the pod bay is operable to receive a plurality of transportation vehicles in batch groupings.
 6. The pod bay of claim 1, further comprising one or more connectors operable to transfer resources to the transportation vehicle.
 7. The pod bay of claim 6, wherein one or more connectors comprise resource transfer manifolds arranged on a ceiling of the pod bay so as to connect with an upper surface of the transportation vehicle.
 8. The pod bay of claim 1, further comprising at least one track operable to support the transportation vehicle.
 9. The pod bay of claim 8, wherein the at least one track is operable to support the transportation vehicle in a levitated state relative to the at least one track.
 10. The pod bay of claim 8, wherein the at least one track is operable to support the transportation vehicle in a landed state on the at least one track.
 11. A portal branch for receiving a plurality of transportation vehicles in the high-speed, low-pressure transportation system, the portal branch comprising a plurality of pod bays according to claim 1, wherein the plurality of pod bays are provided along a shared transportation vehicle path so that a plurality of transportation vehicles are connectable to the plurality of pod bays in batch groupings.
 12. The portal branch of claim 11, comprising a passenger platform arranged adjacent the shared transportation path, the passenger platform providing the loading area for each of the pod bays.
 13. The portal branch of claim 11, comprising a gate valve at each end of the shared transportation path.
 14. A transportation station for off-loading and loading of passengers and/or cargo to a transportation vehicle, the station comprising: a receiving passage for receiving incoming transportation vehicles; a departing passage for sending outgoing transportation vehicles; and a plurality of the portal braches of claim 11, each connected to the receiving passage and the departing passage.
 15. The transportation station of claim 14, wherein respective shared transportation paths of the plurality of portal branches extend parallel to each other.
 16. A method of operating a pod bay in a high-speed, low-pressure transportation system, the method comprising: receiving a transportation vehicle in the pod bay; and connecting at least one airdock arranged in the pod bay with the transportation vehicle, wherein the airdock provides a pathway for off-loading and loading of passengers and/or cargo to the transportation vehicle, wherein the pod bay is operable to maintain the transportation vehicle in a low-pressure environment of the transportation system while the transportation vehicle is connected via the airdock to a boarding area.
 17. The method of claim 16, wherein the connecting comprises attaining a soft capture between the airdock and the transportation vehicle and attaining a hard capture between the airdock and the transportation vehicle.
 18. The method of claim 16, further comprising cycling an internal volume of the airdock between the low-pressure environment of the transportation system and a pressure of the boarding area while the transportation vehicle is connected via the airdock.
 19. The method of claim 18, further comprising opening a bulkhead door connecting the airdock to the boarding area once pressure in the internal volume of the airdock equalizes with the pressure of the boarding area and a pressure of an internal volume of the transportation vehicle.
 20. The method of claim 16, wherein the at least one airdock comprises two airdocks per transportation vehicle. 